Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

YQL-17542 clarify sending stats condition in compute actor #1015

Merged

Conversation

zverevgeny
Copy link
Collaborator

No description provided.

@zverevgeny zverevgeny requested review from resetius and Darych January 15, 2024 15:54
@zverevgeny
Copy link
Collaborator Author

pr over contrib: https://a.yandex-team.ru/review/5162297/details

Copy link

github-actions bot commented Jan 15, 2024

Note

This is an automated comment that will be appended during run.

🔴 linux-x86_64-relwithdebinfo: some tests FAILED for commit 6666344.

Test history

TESTS PASSED ERRORS FAILED SKIPPED MUTED?
59895 50672 0 1 9206 16

🔴 linux-x86_64-release-asan: some tests FAILED for commit 6666344.

Test history

TESTS PASSED ERRORS FAILED SKIPPED MUTED?
15877 15749 0 22 96 10

switch(condition) {
case ESendStats::IfPossible:
if (dT < RuntimeSettings.ReportStatsSettings->MinInterval) {
return;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Дело вкуса конечно. Я бы вместо return дернул функцию, которая непосредственно делает отсылку статистики (тот кусок кода что ниже). Тогда бы условия внутри switch читались проще имхо.

@zverevgeny zverevgeny merged commit 477e168 into ydb-platform:main Jan 22, 2024
2 of 4 checks passed
@niksaveliev niksaveliev mentioned this pull request Jan 29, 2024
@vitstn vitstn mentioned this pull request Jan 29, 2024
@starlinskiy starlinskiy mentioned this pull request Feb 12, 2024
@vitstn vitstn mentioned this pull request Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants